chore: add job-level permissions to all CI workflows#2135
Conversation
|
Detected changes to the release files or to the check-files action |
|
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS |
|
Detected changes to the release files or to the check-files action |
|
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS |
|
Detected changes to the release files or to the check-files action |
|
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS |
texastony
force-pushed
the
refactor-ci-workflow-permissions
branch
from
af44368 to
69e9d34
Compare
|
Detected changes to the release files or to the check-files action |
|
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS |
Co-authored-by: Rishav karanjit <karanjitrishav4@gmail.com>
|
Detected changes to the release files or to the check-files action |
|
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS |
2 participants
Add job-level permissions to every workflow job that didn't already have a permissions block. This follows the principle of least privilege by scoping permissions at the job level rather than relying solely on workflow-level defaults.
Each new permissions block includes:
contents: readpull-requests: writeid-token: writeJobs that already had a permissions block were left untouched.
22 files modified, 113 jobs updated.